home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Loadstar 128 18
/
q18.d81
/
t.autopro boot
< prev
next >
Wrap
Text File
|
2022-08-28
|
11KB
|
201 lines
A U T O P R O 8 0 M O D 3.5
by Jane M. Voskamp of South Australia
The world can be divided into two types of people; those who divide the
world into two types of people and those who don't. In this case I'm
dividing the world into beginners and non-beginners because we have a
program for each. Jane Voskamp's AUTOPRO 80 is a program for beginners. On
this same issue we have MAGIC 128 by e. g. bell which is for those who are
comfortable with Commodore DOS and want raw power.
The main feature of AUTOPRO 80 is the Autoboot Track Creation and
Protection. On the disk that came with your C-128 is a small program called
"autoboot maker" that writes code on Track 1 Sector 0 of a disk. You enter
the name of the file you want booted and this disk will now "autoboot",
meaning that when you turn on (or reset) your computer with this disk in the
drive, the file is automatically booted.
The only problem is that the sector is not firmly "allocated" by the
BAM (Block Allocation Map). If you do a "collect" (or as it is commonly
known, "validate") on that disk, the sector becomes "de-allocated" and any
file saved on that disk can overwrite that sector. This means, no more
autoboot. Worse, if you try to redo the Autoboot on that disk, it will
overwrite the file that overwrote it! Goodbye, file!
AUTOPRO 80 gets around this altogether by first checking if the boot
sector is used. If it is used, the program will de-allocate the sector, and
continue the collect. When the collect is complete, the routine
re-allocates the boot sector, and because it is protected in the BAM with
the Protect (USR) file in the Directory, it can never be accidentally
written over. AUTOPRO 80 even checks for Boot sectors on older disks that
don't have the protect file, and allocates them correctly.
But AUTOPRO 80 is more than just an improved Autoboot maker. It also
provides a friendly atmosphere for performing DOS commands like SCRATCH,
RENAME, FORMAT, and for changing drives. All AUTOPRO 80 routines will work
on 1541, 1571 and 1581 disk drives, as device 8 through 16.
This program uses Jon Mattson's CONTROL 80 (from LS 128 #10) which
makes things like storing and recalling screens easy. Because of CONTROL
80, AUTOPRO 80 is very "windowy". Jane's text, which follows, explains
everything in detail.
The Main Menu
-------------
F1 - Directory F2 - Collect BootDisk
F3 - Rename File F4 - Scratch File
F5 - Protect Boot F6 - Make AutoBoot
F7 - Format Disk F8 - Exit AUTOPRO 80
C=F1 - Change Device# C=F3 - Device Mode 71/41
After an option has finished, or you've exited the routine, a Status
Report window is displayed. If no operation has been performed, or the
Status is 'OK', the window will disappear with a beep. If there has been an
error, or any problems during the routine selected, the Error Message and
DOS (Disk Operating System) status are shown. You are prompted to check
your disk (write protected, disk missing, drive door not closed, etc.),
then press any key to get a new Status and Exit to the Menu. The routines
contain extensive error checking for possible problems.
All the options are easy to use, and most have self-contained
instructions, options or Exits to the Menu. At almost any prompt that asks
for input, if you just press RETURN without entering anything, you'll be
taken back to the Main Menu and the Status Box displayed.
F1 - Directory
This simply displays the directory of the disk in the current drive.
To stop a long directory from scrolling out of sight, press NO SCROLL.
F2 - Collect BootDisk (Also known as Validate)
On accessing this option, a warning is displayed in the window. Do not
Collect a disk with GEOS files on it, or the File Header Block (Icons),
Off-Page Directory and Index Table pointers will be destroyed. Disks with
GEOS files on them should only be validated with GEOS itself.
Anything that could be destructive in AUTOPRO 80 displays a (y/n)
prompt first. To back out, just press N. If you press Y, the program will
first check for the current device mode, 1541 or 1571. If the device is in
1541 mode, you are cautioned against collecting a 1571 disk in 1541 mode.
You could lose files by doing that. The prompt only shows if you have a
1571 disk drive, and is bypassed altogether with a 1581.
The program will then check for an Autoboot on Track 1, Sector 0. If
none is found, a normal Collect is performed and when done, the program
closes the window and displays the Status Report window and the Menu. If an
error occurs, the Collect will abort and the Status Report window, the Error
message and DOS Status will be displayed.
If the disk does contain an autoboot track the program will first
disable the boot sequence, then perform the Collect or Validate, and when
done, re-enable the boot sequence. Then it's back to the Menu.
One possible problem that could occur during the collect is that after
disabling the Autoboot sequence, the collect encounters corrupted sectors on
the disk and aborts the collect without continuing through the re-enable
Autoboot sequence. The window will close and the Status Report window will
be displayed with error messages. In that case your disk will no longer
autoboot. If this should happen, use F6 (Make AutoBoot) to display the name
of the file, and then replace the boot track.
F3 - Rename File
Enter the filename of the file to be renamed (up to 16 characters) and
press RETURN. Then enter the new name for the file (up to 16 characters),
and press RETURN. When the rename is completed, the directory is
automatically displayed on screen. If an error is detected during renaming,
the program aborts, closes the window and displays the Status Report window,
the Error message and DOS Status.
F4 - Scratch File
If you don't remember the name of the file you want to scratch, enter $
(SHIFT-4) for the directory. Otherwise, enter the filename to be scratched
(up to 16 characters). When a scratch is completed, the directory is
automatically displayed on screen.
F5 - Protect Boot
This option protects the Autoboot Sector by creating a User (USR) file
called "protect", and allocating Track 1 Sector 0 to it on the BAM. 1541
users should use the F6 (Make AutoBoot) before using protect. If the
protect file is not the first file on the directory, the routine will abort
to the Status Report window and the Menu. However, when the USR file is
written and allocated to Track 1 Sector 0, the collect routine is called,
which will check for an Autoboot Sector before commencing. As usual, when
completed, the Directory is automatically displayed on screen.
F6 - Make Autoboot
On accessing this option, a warning is displayed in the window. Any
data stored on Track 1 Sector 0 will be over-written and lost during this
process. At the (y/n) prompt, to back out, just press N. You can make
Autoboots for Machine Language programs or for BASIC programs. In the case
of ML programs the command BOOT is written in the boot sequence with the
program name. For BASIC programs RUN is written instead. If you press Y at
the prompt, the program will first check for an existing boot track, and
then the BAM for any allocation of Track 1 Sector 0. Which means you can
create boot tracks on older disks as well. If an autoboot track or a
disabled autoboot track exists, the filename is displayed in the window. At
either of the (y/n) prompts, you can back out. If another program occupies
the sector then you are warned by a message. At the (y/n) prompt you should
select N to exit so as not to overwrite an existing program in this case.
If all is well, the program then prompts you to enter the name of the
program (up to 16 characters) to be autobooted. Do not use punctuation such
as a colon, a semi-colon or a comma. The program then asks you to enter M
for machine language or B for BASIC. The next window allows you to enter
the boot disk unit number from 8